Location Aware Content Using Presence Information Data Formation with Location Object (PIDF-LO)

ABSTRACT

The format of the Presence Information Data Format-Location Object (PIDF-LO) as defined by the Internet Engineering Task Force (IETF) is extended or modified to accommodate, within the standard PIDF-LO format, an association of geospacial location to XML content on the Internet. A geospacial location is associated with Extensible Markup Language (XML) content on the Internet. The XML content is identified by a universal resource locator (URL), and associated with geospatial location information (either a specific location, zone, or direction). The URL is inserted into a &lt;presence . . . &gt; section of a Presence Information Data Format-Location Object (PIDF-LO) compliant document as defined by the Internet Engineering Task Force (IETF). In this way, geospacial location information is associated with Internet based XML content using a standard PIDF-LO format.

The present application claims priority from U.S. Provisional Application No. 60/766,227, entitled “Location Aware Content”, to Donald Le Roy Mitchell, Jr., filed Jan. 2, 2006, the entirety of which is expressly incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to wireless and long distance carriers, Internet Service Providers (ISPs), and information content delivery services/providers and long distance carriers. More particularly, it relates to location services for the wireless industry.

2. Background of Related Art

Location information regarding subscribers is becoming increasingly available in a wireless network. Location information relates to absolute coordinates of a wireless device.

FIG. 6 shows a conventional LoCation Services (LCS) request.

In particular, as shown in FIG. 6, a location server 106 requests location information regarding a particular mobile subscriber (MS) from a core network node, e.g., from a Mobile Switch Center (MSC) 110. Requested information regarding a particular wireless device (MS) may include, e.g., attach, detach, and location area update. The location server 106 may also request information regarding the wireless device such as attach, detach and/or location area update from a Packet Data Node (e.g., SGSN, GGSN, or PDSN), or help the device calculate x/y direction. Typically, location information regarding a particular wireless device is requested of a home location register (HLR).

As shown in step 1 of FIG. 6, a locations services client 104 sends a message to a location server 106.

In step 2, the location server 106 sends a Provide Subscriber Info message to a Home Location Register 108, requesting subscriber information regarding a particular subscriber.

In step 3, the carrier's Home Location Register (HLR) 108 provides the subscriber information for the requested subscriber back to the location server 106.

In step 4, location information regarding the requested subscriber is requested to either an MSC or Packet Data node 110. The MSC or Packet Data Node preferably provides precise location information using, e.g., a global positioning satellite (GPS), triangulation techniques, or other relevant locating technology, or helps the device calculate X/Y direction.

In step 5, the location request is forwarded to the Radio Access Network (RAN) 112 if needed.

In step 6, precise, updated location information regarding the requested subscriber is sent to the location server (LS) 106.

In step 7, an ultimate response to the original location request is sent to the LCS client 104 that initially requested the location information.

Secure User Plane for Location (SUPL) is a standards-based protocol that has been developed to allow a mobile handset client to communicate with a location server, e.g., as shown in step 1 of FIG. 6. The SUPL specification is defined by the Open Mobile Alliance (OMA) standards working group. Refer to OMA Secure User Plane Location Architecture document, OMA-AD-SUPL-V1_(—)0-20060127-C for more details on OMA SUPL call flows; and OMA User Plane Location Protocol document, OMA-TS-ULP-V1_(—)0-20060127-C. The OMA SUPL Version 1 specifies two basic types call flows: (1) a SUPL network initiated (NI) call flow, and (2) a SUPL set initiated (SI) call flow. According to the SUPL standard, a session ID has a unique value consisting of server and handset portions.

The conventional Presence Information Data Format-Location Object (. PIDF-LO) was developed by the GEOPRIV working group, and is the Internet Engineering Task Force (IETF) recommended way to encode location information. Location information in PIDF-LO format may be implemented in a variety of ways, including in presence based systems, and in the context of emergency services and other location based routing applications.

The PIDF-LO format provides for an unbounded number of tuples. (A “tuple” generally relates to a group of anonymous data values traveling together. The word is a generalization of the sequence: couple, triple, quadruple, quintuple, sextuple, etc.)

The geopriv element resides inside the status component of a tuple, hence a single PIDF document may contain an arbitrary number of location objects, some or all of which may be contradictory or complementary. The actual location information is contained inside a <location-info> element, and there may be one or more actual locations described inside the <location-info> element.

Generally speaking, the structure of a PIDF-LO can be depicted as follows:

PIDF-LO document entity (person) tuple 1 status geopriv location-info civicAddress location tuple 2 tuple 3

The conventional PIDF-LO format provides information relating to location, time and status to individuals and entities. The PIDF-LO structure is intended for use with standardized Internet protocols, including Internet protocol (IP), Session Initiation Protocol (SIP), and Simple Object Access Protocol (SOAP).

For multi-media communications using Session Initiation Protocol (SIP), the location of a caller can be indicated in PIDF-LO format. SIP is an Internet Engineering Task Force (IETF) standard protocol for initiating an interactive user session that involves multimedia elements such as video, voice, chat, gaming, virtual reality, etc. SIP is specified in IETF Request for Comments (RFC) 3261 (replacing 2543). Like HTTP or SMTP, SIP works in the application layer of the open systems interconnection (OSI) communications model. SIP can also be used to invite participants to sessions that do not necessarily involve the initiator. Because SIP supports name mapping and redirection services, it makes it possible for users to initiate and receive communications and services from any location, and for networks to identify the users wherever they are. SIP is a request-response protocol dealing with requests from clients and responses from servers. Participants are identified by SIP universal resource locators (URLs). Requests can be sent through any transport protocol, such as UDP, SCTP, or TCP. SIP determines the end system to be used for the session, the communication media and media partners, and the called party's desire to engage in the communication. Once these are assured, SIP establishes call parameters at either end of the communication, and handles call transfer and termination.

FIG. 7 shows a conventional Presence Information Data Format-Location Object (PDIF-LO) format document, as defined by the Internet Engineering Task Force (IETF).

In particular, FIG. 7 shows an example of civic and geospatial location information use in conventional PIDF-LO format document. In the given example, an entity named Mike is visiting his Seattle office and connects his laptop into an Ethernet port in a spare cube. In this case the location is a geodetic location, with the altitude represented as a building floor number. The main location of user is inside the rectangle bounded by the geodetic coordinates specified. Further that the user is on the second floor of the building located at these coordinates.

Of particular note in FIG. 7 is that the entity list is conventionally used to identify a physical entity:

entity=“pres:mike@seattle.example.com”

Generally speaking, conventional PIDF-LO presence lists are used to identify a person. An example person entity=Dontelecomsys.com and a corresponding example name=is “Don Mitchell”.

SUMMARY OF THE INVENTION

A method and apparatus for tying a geospacial location to Extensible Markup Language (XML) content on a network comprises identifying a universal resource locator (URL) of XML content to be tagged with geospacial location information. The URL is inserted into a <presence . . . > section of a Presence Information Data Format-Location Object (PIDF-LO) compliant document as defined by the Internet Engineering Task Force (IETF). Geospacial location information is associated with the XML content.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings, in which:

FIG. 1 shows relevant elements associating MIME type content on the Internet to a geographic location while also correlating other descriptive indexing terms within a modified standards based Extensible Markup Language (XML) based PIDF-LO structure as defined by the Internet Engineering Task Force (IETF), for use with standardized Internet protocols such as IP, SIP and SOAP, in accordance with the principles of the present invention.

FIGS. 2 and 3 show message flow between the relevant elements associating MIME type content on the Internet to a geographic location, as shown in FIG. 1.

FIG. 4 shows exemplary presence lists for a Modified Presence Information Data Format-Location Object (Modified PIDF-LO) document for use in tying MIME type logical content to a geospacial location, and for tagging the content with descriptive information relating to the content, in accordance with the principles of the present invention.

FIG. 5 shows exemplary presence lists for a location aware content-Modified Presence Information Data Format-Location Object (Modified PIDF-LO) for use in tying MIME type logical content to a geospacial location, and for tagging the content with descriptive information relating to the content, in accordance with the principles of the present invention.

FIG. 6 shows a conventional LoCation Services (LCS) request.

FIG. 7 shows a conventional Presence Information Data Format-Location Object (PDIF-LO) format document, as defined by the Internet Engineering Task Force (IETF).

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention extends and modifies the otherwise conventional format of the Presence Information Data Format-Location Object (PIDF-LO) format as defined by the Internet Engineering Task Force (IETF). Conventional PIDF-LO document format tags actual people or places with a geospacial location. The otherwise conventional PIDF-LO format is extended or modified to associate a geospacial location to XML content data on a computer network such as the Internet, corporate Intranets, and/or corporate Extranets.

In particular, content on a computer based network (e.g., Multimedia Internet Message Extensions (MIME) type content) is associated with a geographic location. Thus, instead of associating with a person, the invention associates location with content, e.g., Internet XML content.

In accordance with the disclosed embodiments, content is referenced using a modification to the otherwise conventional PIDF-LO format as follows. A location is associated with Internet based XML reference content using a modified PIDF-LO format using the otherwise conventional <presence . . . > section lists elements. Elements used include the “entity”, “src” and/or “name” fields are modified to associate a location with Internet based XML content.

As an example, the “entity=” element of the PIDF-LO format may be referenced as, e.g., entity=“pres:http://ow.com/S.png”.

Similarly, the “name=” element may be referenced as, e.g., name=“weather: hurricane season, century:1800, season:fall, year:1842”.

The “src=” element may be referenced as, e.g., http://ow.com/s.png.

Individuals and entities are referenced in the conventional PIDF-LO format by a universal resource indicator (URI), e.g., “pres:mike@samplecarrier.com”. As modified herein to associate location to Internet based content, words are included within the content to indicate an active reference to the relevant content subject. These words may be inserted, e.g., in the <meta name “keywords”> section of an HTML document.

Location may be associated to Internet based XML content using an XML based structure either (a) using Simple Object Access Protocol (SOAP); or (b) using Session Initiation Protocol (SIP).

Exemplary specific location aware (“Location”) content tags include, e.g., a specific location identified by latitude and longitude (lat/lon); or a specifically defined zone.

A location zone may be defined, e.g., using a coordinate based polygon system. A suitable coordinate based polygon is disclosed and described in co-owned and co-pending U.S. patent application Ser. No. 11/442,254, filed May 30, 2006, entitled “Voice Over Internet Protocol (VoIP) E911 Metro Street Address Guide (MSAG) Validation”; which claims priority from 60/685,075, filed May 27, 2005, entitled “Voice Over Internet Protocol (VoIP) E911 Metro Street Address Guide (MSAG) Challenges”, by Timothy J. Lorello, the entirety of both of which are expressly incorporated herein by reference.

A coordinate based polygon system defining location zone may have an assigned numbering system. For example, the assigned number “1.0.0.0” may be used to indicate a four (4) square kilometer (Km) area with an assigned centroid lat/lon; the assigned number “1.1.0.0” may be used to indicate a two (2) square Km area with an assigned centroid lat/lon; the assigned number “1.1.1.0” may be used to indicate a one (1) square Km area with an assigned centroid lat/lon; and the assigned number “1.1.1.1” may be used to indicate a one-half (0.5) square Km area with an assigned centroid lat/lon.

Location may be defined directionally, e.g., as “north”, “south”, “east”, “west”, etc.

In accordance with another aspect of the invention, XML content (e.g., photos on the Internet) can be provided with descriptive information using location aware content tags included in the presence information of a PIDF-LO document. Exemplary location aware content tags include, e.g., “Time Reference”, “Weather Reference”, and/or “Descriptive Reference” tags.

Regarding various content types, several protocols allow the use of data representing different ‘media’ such as text, images, audio, and video, and within such media different encoding styles, such as (in video) JPEG, GIF, IEF, and TIFF. The Multimedia Internet Message Extensions (MIME) protocol defines several initial types of multimedia data objects, and a procedure for registering additional types with the Internet Assigned Numbers Authority (IANA): text, images, audio and video.

FIG. 1 shows relevant elements associating MIME type content on the Internet to a geographic location while also correlating other descriptive indexing terms within a modified standards based XML based PIDF-LO structure as defined by the Internet Engineering Task Force (IETF), for use with standardized Internet protocols such as IP, SIP and SOAP, in accordance with the principles of the present invention.

In particular, FIG. 1 shows elements in a given network relevant to associating location to XML content in an Internet network. Content 100 on a relevant network server is associated with location by network elements, including a user agent 101, an application server 102, a content proxy 104, a presence server 105, a profile database 103, a geographic information server (GIS) server 106, a user plane server 107, a global positioning satellite (GPS) 108, and a menu of locations 109.

FIGS. 2 and 3 show message flow between the relevant elements associating MIME type content on the Internet to a geographic location, as shown in FIG. 1.

In particular, in step 1 of FIGS. 2 and 3, content 100 is sent to the content proxy 104 using an XML/SOAP interface. The content 100 may be, for the sake of example, http://otiswyres.com/imaqes/sun.pnq”. The transaction uses an XML based Modified Presence Information Data Format-Location Object (MPIDF-LO) as described herein.

In step 2, the content proxy 104 passes the universal resource locator (URL) of the content 100 to the presence server 105.

The presence server 105 establishes a record of the content 100 and all associated tags.

In step 3, the presence server 105 sends a lat/lon or polygon “Request” to the GIS server 106. The lat/lon relates to a location of the content 100.

In step 4, the GIS server 106 determines the polygon ID associated with the provided lat/lon of the content 100.

In step 5, the GIS server 106 returns back the determined polygon ID.

In step 6 a, the user starts up a main application on the user agent 101, selects an instance to run, and (as shown in steps 6 b-6 d) the Location type, and passes relevant logon information to the application server 102.

In step 6 b, the assisted global positioning system “aGPS” and a user plane server 107 (e.g., a SUPL server with aGPS) in a carrier network provide location. Alternatively, as shown in step 6 c, a BLUETOOTH™ GPS 108 may provide location. Another alternative, shown in step 6 d, allows the user to select a location from a menu of locations, e.g., “Paris”, “Camaria”, etc. 109.

In step 7, the application server 102 looks up the user profile for the application instance, and completes the logon process. Profile data is passed from the profile database 103 back to the application server 102.

In step 8, the user agent 6 a receives location from the source (step 6 b, 6 c or 6 d).

In step 9, the user agent 101 sends its location to the GIS server 106, e.g., “user ‘X’ indicates that ‘I am here’”.

In step 10, the GIS server 106 identifies the polygon within which the user agent 101 is currently located.

In step 11 a, the GIS server 106 passes the identified polygon ID to the application server 102, e.g., “user ‘X’ is in this polygon at this absolute position”.

In step 11 b, the GIS server 106 returns the identified polygon ID and lat/lon of the polygon centroid to the user agent to the application on the user agent 101.

In step 12, the application server 102 requests identification of what content has presence in the identified polygon for this application instance. For example, a list of content with presence in this polygon may be provided, for this application instance, and within the relevant user profile.

In step 13, the presence server 105 returns to the application server 102 a list of content (or content tags) relevant to the user profile, this application instance, and this polygon ID, e.g., the URL of content with presence for this polygon [or content type tags only].

In step 14 a, the application server 102 uses the URL for each element in the list of content and sends a URL request (e.g., hyper-text transfer protocol (HTTP)) to the relevant content 100. Or, as shown in step 14 b, the application server 102 requests content type tags from the user agent 101. Or, as shown in step 14 c, the application server 102 requests from the user agent 101 the identity or URL of content.

In step 15 a, the requested content is returned to the application server 102, or the content URL from step 14 c is relayed from the application.

In step 15 b, the user agent 101 requests the content for each element, e.g., via Hyper Text Transfer Protocol (HTTP) and the URL of requested content.

In step 16, the content is returned to the application on the user agent 101 directly from the content source 100, or from the application server 102.

In step 17, the application on the user agent 101 displays or otherwise utilizes the received content.

FIG. 4 shows exemplary presence lists for a Modified Presence Information Data Format-Location Object (Modified PIDF-LO) document for use in tying MIME type logical content to a geospacial location, and for tagging the content with descriptive information relating to the content, in accordance with the principles of the present invention.

In particular, as shown in FIG. 4, an otherwise conventional PIDF-LO format is modified to use the “entity=”, “name=”, and “src=” lists in the presence section of a modified PIDF-LO format to identify XML content. In this particular example, the XML content is identified as:

entity=“pres:http://otiswyres.com/images/SunfromPlane.png”

src=http://otiswyres.com/images/SunfromPlane.png”

and within the first tuple is:

srsName=“http://www.opengis.net/gml/srs/epsg.xml#4326

Note also in FIG. 4 the addition of descriptive tags to XML content. Predefined tags in this example are “weather”, “century”, “season” and “year”.

name=“weather:hurricane season, century: 1800, season: fall, year: 1842”

Thus, the location aware content defined by the “entity=” list in the presence section of the MPIDF-LO document is further modified with a description of hurricane season, 1800 century, fall season, and 1842.

FIG. 5 shows exemplary presence lists for a location aware content-Modified Presence Information Data Format-Location Object (Modified PIDF-LO) for use in tying MIME type logical content to a geospacial location, and for tagging the content with descriptive information relating to the content, in accordance with the principles of the present invention.

In particular, as shown in FIG. 5, an otherwise conventional PIDF-LO format is modified to use the “entity=”, “name=”, and “src=” lists in the presence section of a modified PIDF-LO format to identify XML content. In this particular example, the XML content is identified as:

entity=&Itimg

src=http://otiswyres.com/images/SunfromPlane.png

name=“Sun from Plane”

and within the first tuple is:

srsName=“http://www.opengis.net/gml/srs/epsg.xml#4326”

Note also in FIG. 5 the addition of descriptive tags to XML content. As in the example of FIG. 4, Predefined tags in the example of FIG. 5 are “weather”, “century”, “season” and “year”.

tag:weather=“hurricane”

tag:century=“1800”

tag:season=“fall”

tag:year=“1842”

Thus, the location aware content defined by the “entity=” list in the presence section of the MPIDF-LO document is further modified with a description of hurricane, 1800 century, fall season, and 1842.

While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention. 

1-30. (canceled)
 31. A method of tying a geospacial location to Extensible Markup Language (XML) content on a network, comprising: receiving, at a physical network server, an XML based document as defined by the Internet Engineering Task Force (IETF), said XML based document lacking geospacial location information identifying a specific physical zone; in response to a determination that said XML based document lacks said geospacial location information, identifying a universal resource locator (URL) of XML content to be tagged with said geospacial location information; requesting said geospacial location information, through said physical network server, for said XML content; associating, at said physical network server, said geospacial location information with said XML content; and inserting, at said physical network server, said XML content and said associated said geospacial location information into a <presence . . . > section of said XML based document.
 32. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said XML content and its associated said geospacial location information is inserted in an “entity=” list in said <presence . . . > section of said XML based document.
 33. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 32, wherein: said XML content and its associated said geospacial location information is also inserted in a “src=” list in said <presence . . . > section of said XML based document.
 34. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said XML content and its associated said geospacial location information is inserted in a “src=” list in said <presence . . . > section of said XML based document.
 35. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said XML content and its associated said geospacial location information is inserted in a “name=” list in said <presence . . . > section of said XML based document.
 36. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said specific physical zone is defined using a coordinate based polygon system.
 37. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 36, wherein: said coordinate based polygon system is defined using an assigned numbering system.
 38. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said geospacial location information identifies a specific latitude/longitude.
 39. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said geospacial location information is defined directionally.
 40. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said network is an Internet.
 41. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said network is a corporate Intranet.
 42. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said network is a corporate Extranet.
 43. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said XML content comprises text.
 44. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said XML content comprises images.
 45. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said XML content comprises audio.
 46. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said XML content comprises video.
 47. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, wherein: said XML content is Multimedia Internet Message Extensions (MIME) type content.
 48. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 31, further comprising: tagging descriptive information relating to said location aware XML content in said <presence . . . > section of said XML based document.
 49. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 48, wherein: said tagged descriptive information is included in said <presence . . . > section of said XML based document.
 50. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 48, wherein: said tagged descriptive information includes at least one of: “weather”, “century”, “season”, and “year” tags.
 51. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 48, wherein: said tagged descriptive information includes at least one of: “Time Reference”, “Weather Reference”, and “Descriptive Reference” tags.
 52. A method of tying a geospacial location to Extensible Markup Language (XML) content on a network, comprising: receiving, at a physical network server, an XML based document as defined by the Internet Engineering Task Force (IETF), said XML based document lacking geospacial location information identifying a specific physical zone; in response to a determination, at said physical network server, that said XML based document lacks said geospacial location information, identifying a universal resource locator (URL) of XML content to be tagged with said geospacial location information; requesting, at a physical network server, said geospacial location information for said XML content; associating, via a Session Initiation Protocol (SIP) protocol, said geospacial location information with said XML content; and inserting, at said physical network server, said XML content and said associated said geospacial location information into a <presence . . . > section of said XML based document.
 53. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said XML content and its associated said geospacial location information is inserted in an “entity=” list in said <presence . . . > section of said XML based document.
 54. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 53, wherein: said XML content and its associated said geospacial location information is also inserted in a “src=” list in said <presence . . . > section of said XML based document.
 55. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said XML content and its associated said geospacial location information is inserted in a “src=” list in said <presence . . . > section of said XML based document.
 56. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said XML content and its associated said geospacial location information is inserted in a “name=” list in said <presence . . . > section of said XML based document.
 57. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said specific physical zone is defined using a coordinate based polygon system.
 58. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 57, wherein: said coordinate based polygon system is defined using an assigned numbering system.
 59. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said geospacial location information identifies a specific latitude/longitude.
 60. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said geospacial location information is defined directionally.
 61. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said network is an Internet.
 62. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said network is a corporate Intranet.
 63. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said network is a corporate Extranet.
 64. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said XML content comprises text.
 65. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said XML content comprises images.
 66. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said XML content comprises audio.
 67. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said XML content comprises video.
 68. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, wherein: said XML content is Multimedia Internet Message Extensions (MIME) type content.
 69. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 52, further comprising: tagging descriptive information relating to said location aware XML content in said <presence . . . > section of said XML based document.
 70. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 69, wherein: said tagged descriptive information is included in said <presence . . . > section of said XML based document.
 71. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 69, wherein: said tagged descriptive information includes at least one of: “weather”, “century”, “season”, and “year” tags.
 72. The method of tying a geospacial location to Extensible Markup Language (XML) content on a network according to claim 69, wherein: said tagged descriptive information includes at least one of: “Time Reference”, “Weather Reference”, and “Descriptive Reference” tags. 